| Result code | Value | Meaning |
|---|
| kOTNoError | 0000 | The function completed execution without error. |
| kOTBadAddressErr | -3150 | The specified protocol address was in an incorrect format or contained illegal information. For TCP/IP this means that the address does not exist in the specified domain. |
| kOTBadOptionErr | -3151 | The specified protocol options were in an incorrect format or contained illegal information. |
| kOTAccessErr | -3152 | You do not have permission to negotiate the specified address or options. |
| kOTBadReferenceErr | -3153 | The specified endpoint reference does not refer to a valid endpoint. |
| kOTNoAddressErr | -3154 | You failed to supply an address, or the endpoint could not allocate an address. |
| kOTOutStateErr | -3155 | The endpoint was not in an appropriate state when you called this function. |
| kOTBadSequenceErr | -3156 | You specified an invalid sequence number or a NULL pointer for the call parameter when rejecting a connection request. |
| |
| kOTLookErr | -3158 | An asynchronous event has occurred. If the event has occurred for an endpoint, you can use the OTLook function to find out what event it was or you can use the notifier function if your notifier handles asynchronous events. If the event has occurred for a provider other than an endpoint, the notifier function installed for that provider must handle the asynchronous event . |
| kOTBadDataErr | -3159 | The amount of client data you specified was not within the bounds allowed by the endpoint. |
| kOTBufferOverflowErr | -3160 | The buffer you allocated to store information when this function returns is not sufficiently large to store the incoming data. |
| kOTFlowErr | -3161 | The endpoint is in asynchronous mode, but the flow-control mechanism prevents the endpoint from accepting or sending any data at this time. |
| kOTNoDataErr | -3162 | For an endpoint or mapper, this result is returned when the endpoint is in nonblocking mode, but no data is currently available. For a mapper, this result is returned by the OTLookupName function when no names are found. TCP/IP functions return this result when no data is available, a lookup times out, or a name exists but addresses do not. |
| kOTNoDisconnectErr | -3163 | No disconnection indication is available. |
| kOTNoUDErrErr | -3164 | No unit data error indication currently exists on
this endpoint. |
| kOTBadFlagErr | -3165 | You specified an invalid flag value. |
| kOTNoReleaseErr | -3166 | No orderly release indication currently exists on
this endpoint. |
| kOTNotSupportedErr | -3167 | This action is not supported by this endpoint. |
| |
| kOTStateChangeErr | -3168 | The endpoint is undergoing a transient state change. This error is returned when you call a function while an endpoint is in the process of changing states. You should wait for an event indicating the endpoint has finished changing state and call the function again. (Note that the equivalent state-change error code, TSTATECHNG, is not described in the 1992 X/Open XTI specification.) The provider also returns this error if you attempt to call an "incompatible" function while another operation is still ongoing; for example if you call the function OTSndUData while a call to the OTOptionManagement function is still outstanding. |
| kOTStructureTypeErr | -3169 | You specified an unsupported structure type for the structType parameter of the OTAlloc function. This error is also returned when the structType structure you specify is inconsistent with the endpoint type. |
| kOTBadNameErr | -3170 | You specified an invalid endpoint name. This error is returned by the TCP/IP domain name resolver (DNR) if you specify a bad host name. |
| kOTBadQLenErr | -3171 | You are using this endpoint to listen for connection requests, but when you bound the endpoint, you specified 0 for the qlen field. If you want to use an endpoint to listen for connection requests, the value of the qlen field must be greater than 0. |
| kOTAddressBusyErr | -3172 | As a return value for a call to the OTBind function, this error code indicates one of the following conditions: 1) no dynamic addresses are available for protocols or configuration methods that allow dynamic addressing, 2) you are attempting to bind two connectionless endpoints to the same address, or 3) you are attempting to bind two or more connection-oriented endpoints to the same address and more than one of these endpoints has a qlen field greater than 0. |
| |
| kOTIndOutErr | -3173 | There are outstanding connection indications on the endpoint, and you are accepting a connection for this endpoint. When accepting a connection for an endpoint that is listening for connection requests, you must have responded to all outstanding requests either by rejecting them with the OTSndDisconnect function or by accepting them with the OTAccept function. |
| kOTProviderMismatchErr | -3174 | The endpoint that is to accept the connection is not the same kind of endpoint as the endpoint listening for the connection. The listening and accepting endpoints must be the same kind: either connection-
oriented transaction-based or connection-oriented transactionless. |
| kOTResQLenErr | -3175 | When this endpoint was bound, the qlen field was set to a value greater than 0. But to accept a connection on an alternate endpoint that is bound to the same address, such as this one, the endpoint must be bound with a qlen parameter equal to 0. |
| kOTResAddressErr | -3176 | The address to which this endpoint is bound differs from that of the endpoint that received the connection request; thus, this endpoint cannot accept this connection request. |
| kOTQFullErr | -3177 | The maximum number of outstanding indications, as specified by the value of the qlen field you used when you bound the endpoint, has been reached for the endpoint. |
| kOTProtocolErr | -3178 | An unspecified protocol error occurred. |
| kOTBadSyncErr | -3179 | You called the OTSync function at non-System
Task time. |
| kOTCanceledErr | -3180 | A provider function never finished executing because the provider was closed or because the function was synchronous and synchronous functions were cancelled. |
| |
| kOTNotFoundErr | -3201 | Requested information does not exist. |
| kENOENTErr | -3201 | This error literally means no such file or directory. In XTI (and Open Transport), a function returns this result when you try to open an endpoint or mapper that does not exist in the system. |
| kENIOErr | -3204 | An I/O error occurred. |
| kENXIOErr | -3205 | No such device or address. |
kEAGAINErr | -3210 | The provider cannot perform this operation at this time. Try again later. |
| kENOMEMErr | -3211 | Open Transport cannot allocate enough memory to meet your request. |
| kOTOutOfMemoryErr | -3211 | Open Transport has run out of internal memory. This might happen, for example, if you are doing a lot of asynchronous sends and not acknowledging sends, which means that Open Transport has to copy the data being sent into its own internal buffers. |
| kEBUSYErr | -3215 | The device you are trying to access is busy and could not complete your request. |
kOTDuplicateFoundErr | -3216 | You are attempting to register a port or other entity that already exists. |
| kEINVALErr | -3221 | The specified address had an invalid size. |
| kEWOULDBLOCKErr | -3234 | In order to complete the requested operation, the endpoint provider would have to block, and the endpoint is in nonblocking mode. |
| kETIMEDOUTErr | -3259 | The requested operation timed out. |
| kENOSRErr | -3271 | Open Transport cannot allocate enough system resources (usually stream messages) to meet
your request. |
